Description

When CCExtractor produces no output file, ServerComparer.CompareAndAddToResult() calls File.Open("", FileMode.Open), which throws ArgumentException. The caller in Tester.cs swallows it and unconditionally calls
SendExitCodeAndRuntime() — so the test is marked finished with no TestResultFile row written and no comparison data sent to the platform.

Execution chain

Processor.cs      → rd.ResultFiles.Add(key, "")          // file missing
ServerComparer.cs → File.Open("", FileMode.Open)          // throws ArgumentException
Tester.cs         → catch (Exception e) { Logger.Error } // swallowed
Tester.cs         → SendExitCodeAndRuntime(...)           // runs unconditionally
Platform          → receives finish, no comparison row    // status sees zero failures

Findings

Command run on the sample-platform server:

grep -n "Path is empty" /repository/LogFiles/9298.txt

Logs — [ERROR] Path is empty immediately followed by [INFO] Finished entry X
in 10 production log files (4778, 4782, 4790, 4792, 4794, 4798, 4804, 4828, 5124, 9298). Example from log 9298 (25 occurrences, wc -l verified):

68:[ERROR] Path is empty
69:[INFO] Finished entry 4 with exit code: 0
95:[ERROR] Path is empty
96:[INFO] Finished entry 17 with exit code: 10

Log 9299 (same test, Windows): 0 occurrences — Windows missing rows have a separate unrelated cause not addressed here.

DB — test_result row exists (finish received) but no test_result_file row (comparison never ran), exit_code=0, expected_rc=0, excluding ignored/stdout tests (139, 238, 239):

SELECT t.test_type, COUNT(*) AS confirmed_silent_failures
FROM test_result tr
JOIN test t ON t.id = tr.test_id
LEFT JOIN test_result_file trf
    ON trf.test_id = tr.test_id AND trf.regression_test_id = tr.regression_test_id
WHERE trf.test_id IS NULL AND tr.exit_code = 0 AND tr.expected_rc = 0
  AND tr.regression_test_id NOT IN (139, 238, 239)
GROUP BY t.test_type;

Counts tests where finish was received but no comparison row was written — includes but is not limited to instances caused by this bug.

11 affected regression test IDs (7, 16, 138, 140, 143, 144, 145, 148, 150, 154, 155) all have thousands of historical TestResultFile rows, confirming this is a runtime failure not a data model gap.

Fix

Add a guard inside the !Hasher.filesAreEqual branch that checks string.IsNullOrEmpty(data.ProducedFile) || !File.Exists(data.ProducedFile) and returns early, preventing File.Open("") from being called.

Impact

Risks

• No behavior change when output files are produced correctly.
• Does not create a failure-marker TestResultFile row — that requires
  server-side changes and is out of scope.
• This alone does not fix false-positive status reporting — a separate PR on
  sample-platform addresses the counting logic.

Deployment

Independent of sample-platform. Can deploy in parallel with #1118.